The culprit is the "Use Graphics Processor" setting in Performance. Turning it off, which I did a while ago for at least two reasons that I don't recall offhand, kills the Transform box if it falls outside the image area. It has been years now since Apple spun its own silicon, but Photoshop still doesn't play nice with the onboard GPU (or, in this case, without it). I remember the day when Adobe was all about the Mac. Oh well. Now I have to rediscover the reasons for turning it off, then decide which compromise is worse. My bet is that the problematic Transform box will be easier to live with. ... View more

Should have done that already. I admit that I shy away from deleting settings (nee preferences) because there are so many and it is a royal pain-in-the-patootie to reconstruct them. I was hoping there was a solution short of that. So, yes, the transform box shows on the pasteboard when using default settings (screenshot attached). The center control is missing, though. It can be brought back in the Tools settings, but it is different. It doesn't even look like just another control point (second screenshot, with gray pasteboard instead of black). Now I need to reconstruct all my settings and check the Transform box along the way. That's for another day, but I will post what I find. (And thanks, Scott. I guess 😉 ... View more

Yeah, wish it did, but no. However, Chuck (in the next post) is onto something. ... View more

I know that you were looking for handles to appear if the zoom was small enough. (They don't.) That was already shown in what I posted. My third screenshot shows the image when it is too wide for the canvas, but not too tall. The handles on the canvas are visible. The handles at the ends of the image are on the pasteboard and are not visible. Yes, it is time to bark up a different tree. But thanks for the consideration! ... View more

OK, this is it, though. If you want to explore it further, you should do similar test yourself. Can you see handles on the pasteboard? If yes, then there's something about my setup. If no, then this is a problem that somehow has gone unnoticed. (I didn't post back when I first noticed it. All to often, posting ends up going around in circles.) ... View more

No, I appreciate your interest, but it is easy to see that the handles in the first screenshot are not there. Just the center spot. Apply some logic. 4x the 25% image is obviously larger than the canvas. All I did was scale it down to 25% to show the handles. This is not my first rodeo. Clearly, no one in this community that has seen my post has any idea about it. Strange. It's the kind of thing that would usually bring up a chorus of users. ... View more

The first screenshot shows a single layer with a sunset sky on it. The sky is larger than the canvas. I hit Command-T to scale it down. Only the center control point is visible. The rest of the Transform box, which falls outside the canvas (but is smaller than the visible pasteboard) is not shown. Historically, it used to be. It disappeared in some recent update to Photoshop. (Recently, meaning within the last year or so. I've used Photoshop since the early '90s.) The second screenshot shows the same sky image scaled down enough that the entire Transform box is visible.             ... View more

Thanks again. I searched quite a bit using various terms, but could find nothing relevant to my particular problem. I gather that GPU issues show up in different ways for different users. I would not have connected the "native canvas" (whatever that is) with a GPU problem, nor with the problem I reported. It was a problem in Ventura, too, not just Sonoma, but I lived with it when initial searches of this forum were fruitless. I finally made my own post, which is why contributors such as yourself keep having to supply the same solution over and over. ... View more

Awesome, Kevin! Thanks so much! Yes, that did the trick. Oddly, it wasn't flicker or stretch in the slightest, and the affected image(s) never went black. (Hence, my futility at finding the post.) But "Disable Native Canvas" appears to cure all. The problem was also present in Ventura. I leapfrogged from Mojave (on Intel) to Ventura/Sonoma (on Apple Silicon) this year, and there have been various strange defects, some more pernicious than others. For example, in InDesign, GPU Performance was off by default and had to be enabled to fix a problem where any kind of drag-selecting of objects or text caused the item(s) to disappear. One would hope that Adobe (and/or Apple) would fix problems reasonably soon after they are revealed, but it's been hit-or-miss since the beginning in the 80s. ... View more

That may be the Apple Silicon effect. Anyway, I turned off rulers, which of course, works. But better is enabling GPU performance (which allows rulers). It didn't even occur to me that GPU performance might be off by default, or that it might have anything to do with the problem. The tangled web we weave! Well, Adobe/Apple anyway. ... View more

Well, that was kind of snarky, but thanks for the feedback. I did several searches and this post was what I found. Pray tell what search terms find "countless other threads"? The M2 is not that new. I've been making my living with Adobe products since 1987, but is the Mac now taking a decided backseat to Windows? (Yes, Sonoma is new. I may be conflating things. The Photoshop problem includes Ventura. I leapfrogged from Mojave to Ventura. And, while Illustrator debuted in the 80s, Pagemaker was originally from Aldus, then after Adobe acquired it, was supplanted by InDesign. Rather than revert to Ventura, I am more likely simply to use the 2010 Mac Pro until Adobe and/or Apple get it together.) ... View more

I have a new Mac mini M2 Pro and just upgraded to Sonoma. InDesign 19.0 seems to be working, though I haven’t gotten very far. When drag selecting any item(s), the page goes white (empty). Its contents reappear when the drag is completed. Selecting single or multiple items by clicking (or shift-clicking) on them does not have this problem. The same thing happens while drag selecting text with the text tool. The problem is weirdly similar to a current Photoshop problem, which was also present in Ventura. When more than one Photoshop image is open, the last active image goes blank gray (not grayscale) when a new image is opened or a different open image is made active (clicked on). The blank gray image is corrected when that image is made active again and made to redraw (e.g, moving the window). But then the previously active window goes blank gray. These things never happen on my trusty old 2010 Mac Pro running Mojave. I don’t expect anyone here to have fixes, so this post is simply providing input to the community. ... View more

I received notification today of updates to six apps. It came from Creative Cloud as mac os notifications. Creative Cloud had been quit (one has to ignore the warning it puts up) after turning off all notifications and updates. Installing the updates left Creative Cloud up and running, so I quit it again (which removes it from the menu bar). So for anyone wondering how this all works out, there it is. (I should note that my fully upgraded mid-2010 Mac Pro is running Mojave. It cannot run Catalina.) ... View more

Thanks for the "how to"! I turned off everything that can be turned off in Creative Cloud prefs and quit it. Now it remains to be seen how Mac OS Notifications might help. The only Adobe apps listed in Notifications prefs are for Adobe Acrobat Synchronizer (which I removed from Login Itemes, no need for it as a solo operator), Adobe Desktop Service (the purpose of which is unclear even after searching for info), and Creative Cloud. They are all set to provide alerts, which presumably means I will get an alert when an Adobe CC app I have installed is updated. Time will tell. Crazy how Adobe sabotaged their own alert system, driving users away instead of helping them. ... View more

The red dot notification keeps appearing on the Creative Cloud icon in the mac os menu bar. As Jan2563190 notes, it started doing that fairly recently. Previously it was useful for drawing attention to app updates (which I do manually). Now it shows up over and over every day, and for no apparent reason. Seriously. No apparent reason. And this is despite all notifications being turned off except for app updates. (I just turned that off, too, but doubt it will make any difference.) Syncing is also turned off. For such a small thing, the unwanted and useless red dot is super irritating. The solution may be to uninstall the Creative Cloud app, which appears to be the only way to get its icon off the menu bar. I may end up doing that anyway, but does that also kill being able to update apps? I hestitate to find out. Adobe has not only foisted the red dot imposition on users, it doesn't even bother to provide basic information about this behavior or what can be done about it and what the consequences might be. If anyone from Adobe is reading this, what kind of thinking leads to this kind of situation? That may sound like a rhetorical question, but it's really not. ... View more

Yes, that works. I have such a strong single screen habit (33 years and counting) that I didn't keep using the second screen, or I would set it up like you did. (I have panels and tools hidden until I mouse to the screen edges, similar to the Dock at the bottom edge. And use a lot of keyboard shortcuts.) The second screen was headed to a different (new) Mac anyway. ... View more

Thanks, Rob. That's actually what I described in my first reply above. Except that it's the lower right corner, not lower left. One drawback of this is that if you have two screens, and the interface is on the left screen, the Control bar is displayed on the right screen (other than the tip of it on the left screen, of course). ... View more

Palm smacks forehead. Finally thought to Shut Down and restart from a dead stop. (And run Cocktail on Pilot mode.) Problem solved. Sorry guys! Should have done that sooner. Ironically, way back with OS 9 and earlier, shutting down or restarting was frequently necessary (if the system wasn't already frozen).  In modern times I leapt to the conclusion that a glitch associated with an app update is actually an intentional change to the way Photoshop works. It was just a glitch. A bizarre glitch. ... View more

Hi, D_Fosse. I haven't been a denizen of Adobe user forums much since, well, before iPhone. But I posted a screenshot as an attachment (apparently), and it's there when I return to my original post. Are you not seeing it? (It's a link, not the image itself.) ... View more

Seriously? That's what you come back with? OK, ignore the Save for Web and look at the Layers panel. As for your question, I'd like to ask one in return. Why do you care?  I have many years of muscle memory, keystroke shortcuts, and familiarity with the legacy solution. I've been a freelance designer since the 80s and I'm all but retired now. Save for Web is one of those things that worked just fine, but Adobe in its infinite wisdom decided to "fix" it. The biggest challenge to professionals is the moving target that is the Adobe UI. Like holding Shift to NOT constrain scaling, when it was the opposite for decades. The list is very long, but you get the point. In any event, I would like to find the answer to what I posted, if anyone can shed light. Meanwhile, workflow habits are not the subject of this topic, and I hope no one feels compelled to continue down that vein. ... View more

OK, I have not reinstalled yet. The problem is partially (possibly fully) resolved. The update to 15.0.1 may have addressed the missing Save function. Also, under Preferences > Interface, setting Live Screen Drawing to Immediate solved part of the "misbehavior" I was experiencing with trying to correct overset text (which I was relating to control panel and pointer move functions). I will post again if problems resurface (at which point I will try reinstalling). ... View more

It sure was difficult to find this tip. Virtually no search terms uncovered the solution. Blue popup tips have been showing up all over the place in Acrobat Pro DC (build 19.21.20049.354971), and I don't even use Commenting (ever), much less have it open. Thank you, aguilayserpiente! I agree with your frustration over Adobe's presumptions, though it is far easier to catch more flies with honey than with vinegar. ... View more

Actually, there is a way to display a document in InDesign at what I call “true actual size”, which means if you lay an 8.5x11 sheet of paper over the display of an 8.5x11 page, they will be the same size. Here is what I posted in previous years (last time was 2014), but apparently that has been culled with time. I have updated it for InDesign CC 2020 (Version 15).   How to display at true actual size (Mac) November 21, 2019   The solution to achieving "true actual size" is a script written by Dave Saunders (and probably others) some time ago, If you're like me and don't really use scripts, here is what to do with it on a Mac (with apologies to Dave and other experts who know a helluva lot more about this than I do):   1. Copy the text for this script:   //by Dave Saunders. Replace the percentage number with the correct value for your screen app.layoutWindows[0].zoomPercentage = 113;   2. Paste it into a text file (I used TextEdit) and leave the file open. You will save it later.   3. Go to Acrobat Pro>Preferences>Page Display and under Resolution note the number associated with "Use system setting". (On my system it is 81 pixels/inch. Note that enabling that setting also makes Acrobat display at true actual size. However, there is a long-standing bug with Acrobat that can make Acrobat slow to an agonizing crawl with multi-page PDF files when using this setting, so I use “Custom Resolution” as my default unless I need true actual size.)   4. Divide the number from Acrobat by 72, then multiply by 100. (This is essentially a percentage calculation of system resolution over the conversion value of 72 points/inch, which produces 112.5 in my example. I rounded it to 113.)   5. In the open text file, change the number 113 to what you got from the above step.   6. Save the file with the name “True actual size.jsx” to this location:   Users/[username]/Library/Preferences/Adobe InDesign/[version]/[language]/Scripts/Scripts Panel   Note that the file extension must be .jsx    7. Test the script in an open InDesign document by going to Window>Utilities>Scripts, then click on User and double click on your script. The display should now show your work at true actual size.   8. The Scripts panel is awkward at best, so the last step is to assign a keyboard shortcut to your script. I use Control-1. Go to Edit>Keyboard Shortcuts… and choose Scripts in the Product Area menu. Scroll down to the bottom, where you should see your script listed. Highlight it and enter Control-1 (or whatever you prefer) into the New Shortcut window and click Assign. Then click Save. (You won't be allowed to modify the Default set, but I just went with "Default copy”.)   Now whenever you want to view your work at true actual size, just hit Control-1 (or whatever you chose for a keyboard shortcut).   You might want to copy these instructions into a TextEdit file and save it where you will find it when the time comes to upgrade InDesign CC again, because it’s likely that you’ll need to achieve true actual size all over again.   Lastly and far from least, thank you for the script, Dave! If you or other pros come across this and see corrections or improvements, please set me straight. ... View more

Thanks. I figured as much, but it never hurts to ask in case I overlooked something. Not a very bright move on Adobe's part from my viewpoint. ... View more

I should add that the best I could come up with was detaching it from the top, making it as narrow as possible, then tucking it away in the lower right corner of the screen so that only the left tip is visible. ... View more